General Information Information on the transmitted data. Business unit Location of a branch office. Place/ Location code UN/Locode; e.g. the location of the user's branch office. Location name. If there is no UN/LoCode available for this place, alternatively the name can be set. Communication information. Contains information on sender, recipients and creation time. Communication participants Up to 11 entries can be sent: SENDER - mandatory with DAKOSY-code EDI_PROVIDER - optional; 'DAKOSY', if message should be processed by DAKOSY RECIPIENT - mandatory with DAKOSY-Code. Maximum of nine entries is possible. Date and time of message creation. General Message definition Describes the contents of a message (metainfo and data) Unique Reference Number to identify a single message. Message status original: first message User information Information on the user who sent the message. Metainfo Contains information concerning transaction type, communication parties etc. Transaction type Specifies the transaction type (GM01, AB01 etc.). Only one transaction per file is allowed. Different types must be sent in separate files. Application name Name of the application served by the interface. E.g. SEEDOS, ATLAS Testflag 0 - false (default); 1- true; transmission for test purpose Number of messages Number of messages (elements) that are collected in the transmitted file. Exchange Reference Number, Unique Referenc for each Transmitted file. DAKOSY-code 4-letter code identifying the participant application usage Alias code. Describes how the participant is identified in another system, e.g. DAK as DAKOSY-code. Other identifiers are not specified yet. participant name just for informal use Password Needs only to be set if required by the specified role. SENDER RECIPIENT EDI_PROVIDER ORIGINAL_SENDER Reference Unique Reference Number to identify a single message. First reference always Message reference of the original message ReferenceType MSGREF = Message reference Description DateTime DateTimeType creation receipt Texts Code DAKOSY Code Severity Severity: 0 = information 1 = normal 2 = important 3 = urgent 4 = critical 5 = fatal FreeText Addresses Optional details on SENDER, e.g. Department or Location Not used by now Address ResponseType Transaction name Message provider name of the party who is responsible for the underlying scheme. Version of message definition Message type Code defined by the provider for the specified transaction, e.g. GM01 = customs declaration AC02 = transport order TransaktionType Transaction information Name Phone number plain text without validation. Either phone number or e-mail address must be filled if the user-element is transmitted. E-mail